Configuration File Manager
The Configuration File Manager keeps track of sessions, services, and other managers. All of its data is managed through the tools in the Session menu in the Progress Dynamics Administration window, as shown:
Use the Manager Type Control window to define new manager types and to identify which managers to prestart for which session types. The figure below shows all the managers that come with the framework. Each has a Type Code that you can use as an identifier to run procedures in its API and other information about the manager, as shown:
Use the Session Type Control window to define session types for the different ways in which your application or development environment needs to run. These built-in session types provide you with a variety of ways to start your client and server sessions, including a development environment with or without AppServer and a run-time GUI environment, as shown:
The Service Type Control window lets you define system services that require special code to start and manage them. Progress Dynamics comes with built-in service types for AppServers, for databases, and for Java Message Service (JMS) partitions. Each Service Type defines a management procedure and a maintenance procedure that together provide the code to support the service, using a common API that is part of the Connection Manager, as shown:
You can define any number of specific services for each different service type. For example, for each database your application needs to connect, you can define the startup parameters and other connection information for each service. In the Logical Service Maintenance window you define a logical name or Service Code for each service, that is, for each different database connection and each AppServer connection, as shown:
In the Physical Service Maintenance window, you can define the specific startup parameters for the service, including database connection parameters, host, service, and network names, as shown:
Each Session Type has properties that define characteristics of the session, such as whether it can run on the client only, its startup procedure, and the Propath for the session. You can maintain these in the Session Property Control window and then assign properties and values to different session types, as shown:
You can define Profile types in the Profile Type Control window. Profile types are different categories of user profile information stored in the Repository. Use them to help personalize the interface and behavior of an application for each user, as shown:
The data you maintain with these different utilities is kept in the Repository, but much of it is also written out to an XML file, which allows each session to gain access to the configuration information it needs to start up. Here is a small excerpt from the standard Progress Dynamics XML representation of the configuration data, stored in icfconfig.xml:
